home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga Tools 4
/
Amiga Tools 4.iso
/
tools
/
system-tools
/
fastexec
/
fastexec.doc
< prev
next >
Wrap
Text File
|
1996-02-26
|
6KB
|
220 lines
°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
Januari 14, 1996
Torbjörn Andersson
presents
FastExec 1.1
Shareware
°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
1. Contents
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Contents ................................................. 1
Introduction ............................................. 2
Requirements ............................................. 3
Installation ............................................. 4
Usage .................................................... 5
Comments ................................................. 6
History .................................................. 7
Credits .................................................. 8
Distribution ............................................. 9
2. Introduction
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Most things automatically utilize the fast memory in my
Amiga, but not exec.library, the heaviest used library of
the AmigaOS, nor expansion.library. They remain in the slow
chip memory. Since that is a waste of both time and chip
memory, I made FastExec.
FastExec is meant to be started as the first thing in the
startup-sequence. It will reboot and move exec.library from
the slow chip memory to fast memory.
FastExec is not programmed in a recommended way, because I
don't know any clean way to solve the problem. FastExec may
not work on your system. It does for example not work
together with A570 CD-ROM.
3. Requirements
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FastExec requires true fast memory.
FastExec has been tested with the kickstarts listed below.
It may not work with others.
33.180 (1.2)
34.005 (1.3)
37.175 (2.04)
39.106 (3.00)
4. Installation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Edit Startup-Sequence to start FastExec first.
FastExec will reboot the machine, after that exec.library
will be in fast memory.
5. Usage
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Usage: FastExec [NOCACHE] [NOCOLDCAPTURE]
[FASTVBR|CHIPVBR|MOVEVBR]
[CHIPSTART=0xhhhhhhhh]
[CHIPEND=0xhhhhhhhh]
[CHIPPRI=n]
[BOARDADDR=0xhhhhhhhh ...]
[SYSINFO]
NOCACHE:
MC68020 and better processors has an instruction cache,
which is enabled by the kickstart. The boot code in FastExec
does the same, but this disables the cache instead. Might be
useful with non-DOS games.
NOCOLDCAPTURE:
Clear the ColdCapture vector in ExecBase. Probably useless,
but it helped me with a kickstart loader once.
FASTVBR|CHIPVBR|MOVEVBR:
Change the Vector Base Register from zero to point at fast,
chip or any type of memory. Just like some programs, it has
nothing at all do with the reboot process.
CHIPSTART:
Change start address of chip memory. It is usually $400, or
$1000 on MC68040. Any lower value will not be accepted.
Could be useful with ShapeShifter.
CHIPEND:
Change end address of chip memory.
CHIPPRI:
Priority of chip memory.
(default -10)
BOARDADDR:
Because of the way FastExec reboots, each AutoConfig board
will not appear at $E80000 as they normally do. They will
stay at the addresses they were firstly assigned, and will
therefore not be recognized by the system at the second
boot.
If you for some reason want them in the system list of
AutoConfig boards, this will add them. You can use the
SYSINFO argument to find their addresses (i.e. before using
FastExec). Look at the second field at the bottom of
the output.
SYSINFO:
Shows various system information.
6. Comments
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Don't use the MMU to remap ROM before starting FastExec
(i.e. CPU FASTROM). It's ok to remap ROM after FastExec.
Don't have virtual memory hanging around in your system when
starting FastExec.
If you bring up the bootmenu, exec.library will not be in
fast memory when you boot.
If FastExec doesn't work at all there's probably nothing to
do about it directly, but please contact me via email if you
can. Hopefully it is something I can fix in the program.
7. History
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1.0 (26.11.95)
* First release.
1.1 (14.1.96)
* lib_NegSize under KS 1.3 is now set to correct value and
not 0.
* Doesn't set the memory attribute flags
MEMF_LOCAL/MEMF_24BITDMA under KS 1.3.
* The name string "expansion ram" is used for the fast
memory under KS 1.3, instead of "Fast Memory".
* The priority that the fast memory has will not be changed,
it was always set to 10 before.
* Could get wrong idea of were the kickstart was located,
some checking together with alternative methods makes it
safer now.
* If kickstart version is 2.0 or higher, FastExec will
search through the kickstart for everything it needs from
it. If FastExec will work doesn't depend on the exact
kickstart version, but more on how it is built. If there
aren't too big differences, FastExec should now work with
any kickstart version.
* Changed some output from the SYSINFO argument, and
documented that the argument exists. :)
* BOARDADDR handles more than one address.
8. Credits
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thanks to all registered users.
9. Distribution
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FastExec is made by and copyright Torbjörn Andersson. No
commercial usage is allowed without written permission from
the author. Other distribution is allowed if no files in
the original distribution are removed or modified.
FastExec is not free. If you use it for more than one month
you are requested to register. The suggested fee is US $5
or 20 SEK. Please send the fee to this address:
Torbjörn Andersson
Knöppletorp 4379
S-380 31 LÄCKEBY
SWEDEN
email: d95ta@efd.lth.se
I love you - AMIGA